Add blog post: Filling the Gaps in Terraform-to-Pulumi Migration - #21132

Introduces pulumi-tool-import and its agent skills: the digest → resolve →
import → patch-state pipeline for migrating Terraform (and CDK/CFN)
workspaces onto the AWS Classic provider, with secrets handled via
encrypted stack config, batched failure-isolating imports, state patching
for fields the cloud API doesn't return, and state injection for
non-importable resources. Adds author profile for jonathan-davenport.

Date is a 2099-01-01 placeholder until a publish date is chosen.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Publish date 2026-08-31; social copy for X/LinkedIn/Bluesky (passed
critique review); clarify the tool is a ProServ-maintained Pulumi CLI
tool plugin using the Automation API, not part of the core product.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

…ulty

Reframe the intro and gaps section: migration is doable and the gaps are
mechanical/automatable, with the 4,000-resource self-service customer as
the proof point up front.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Intro concedes migrations are hard but frames the gaps as mechanical and
largely upstream of Pulumi (AWS write-only API design, Terraform
providers shipping without importers), per the root-cause taxonomy in
the tool repo's aws-import-diff-fields.md. Social copy recast so the
customer's 4,000-resource migration reads as enabled by the tool, not
endured despite the gaps.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

…digest

The command requires --state-file and extracts explicitly mapped values
from Terraform state via the same config-writing helpers as the digest's
automatic pass — it is not for secrets outside state.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

The CFN front end is less built out; keep the post focused on the
Terraform workflow.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>